##[group]The deploy tool's tests
npm run test:deploy
##[endgroup]
shell: bash -e /home/runner/_temp/18dfc462ce759040.sh

> test:deploy
> node --test "scripts/deploy/*.test.mjs"

error: no matching package named `base64` found
location searched: crates.io index
required by package `g1t-api v0.1.0 (/home/runner/work/repo/apps/api)`
note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
help: if this error is too confusing you may wish to retry without `--offline`
✔ the manifest matches every wrangler config in the repository (39.214143ms)
✔ every wrangler.jsonc is found, and only checked-in ones (76.222295ms)
✔ problems are found: an unlisted config, a later-stage binding, a wrong database, an unnamed KV (88.792766ms)
✔ stages follow bindings: nothing binds to a unit that ships after it (0.986531ms)
✔ Rust workers build with the shared script and the same wasm-opt level (1.394171ms)
✔ shared crates and packages are read from workspace metadata (0.831151ms)
✔ the runner's image is built from the runner crate and what it uses, on the base its lock names (0.984471ms)
✔ services/runner/base.json records the base its folder builds (12.876871ms)
✔ an image's hash ignores line endings, and its tags say what they are (208.709368ms)
✔ only the lockfile entries the runner is built from name its image (1.047221ms)
✔ the runner's deploy config names its image by reference, beside its wrangler.jsonc (73.024402ms)
✔ the registry is asked for an image's manifest, without Docker (2.181082ms)
✔ a push counts only when it ends with a digest, and is tried again (0.937831ms)
✔ a static Linux binary is told from a dynamic one (1.455151ms)
﹣ path dependencies agree with Cargo's own resolved graph (1091.09647ms) # cargo metadata could not resolve offline
✔ every import that leaves a unit's folder is covered by its dependencies or inputs (108.604513ms)
✔ a shared crate's change reaches every unit built from it, and no other (1.082851ms)
✔ a shared package's change reaches what imports it (0.29995ms)
✔ a crate's tests, benches and examples deploy nothing (0.920661ms)
✔ a Rust file compiled only for tests is found from what declares it (1.399991ms)
✔ this repository's test-only sources are read from git (688.248837ms)
✔ decide: a change only to tests deploys nothing (1.374531ms)
✔ own folders, declared inputs and root files (1.195611ms)
✔ a Cargo.lock change reaches only crates that use what changed (0.377701ms)
✔ a package-lock change reaches through workspace links (0.57685ms)
✔ decide: changed units deploy, others wait, unknown ones deploy (0.33719ms)
✔ decide: --force deploys unchanged units; a commit missing from history deploys (0.810051ms)
✔ decide: Cargo.lock counts only where it reaches (0.624631ms)
✔ decide: the runner's image rebuilds only when what it is built from changed (0.20875ms)
✔ the plan as data: migrations, and each stage's units in jobs that share a build (1.397631ms)
✔ units are picked by short name, folder or Worker name (0.610621ms)
✔ a CI job installs only what its units need (0.86414ms)
✔ a deploy is annotated with its commit, and read back (0.473121ms)
✔ the live commit: the live version's, looking through secret changes (0.36542ms)
✔ Wrangler's output: pending migrations and the version a deploy made (0.339281ms)
✔ the API's answers: the live commit as Wrangler's would give it (0.91439ms)
✔ the API's answers: a Worker never deployed, and a refusal, never throw (502.678749ms)
✔ the API is used only with the token Wrangler would be given (0.41309ms)
✔ pending migrations: the folder's files less the names in d1_migrations (1.865752ms)
✔ the pool runs everything, no more than its limit at once (14.771663ms)
✔ self-hosting builds every Rust service the manifest says it runs (0.787891ms)
✔ docs/SELF_HOSTING.md's table names every unit (0.448801ms)
✔ resolveStack works on a manifest with no workspace crates or packages (3.467713ms)
✔ decide: a commit older than what runs is never deployed by accident, even forced; --rollback means it (0.24255ms)
✔ a deploy by hand reports to the repository on g1t, and a workflow's does not (1.683951ms)
✔ webhooks: the hourly purge deletes old deliveries by time (2.260431ms)
✔ billing: this month's users are read from an index, not the ledger (45.273449ms)
✔ events: a repository's events of one type, newest first, page by page (2.096881ms)
✔ actions: a self-hosted runner's poll finds queued jobs by namespace, whatever its case (10.562049ms)
✔ chat: a channel's messages and a thread's replies, newest first, page by page (1.445801ms)
✔ chat: the sidebar's unread messages are read from each channel's index, after the last read (1.042211ms)
✔ chat: a page's reactions are read by message, and a workspace's emoji by name (1.313811ms)
scheduler: g1t-webhooks (* * * * *) is still running from the last time; skipped
scheduler: g1t-webhooks (* * * * *): 200 {"outcome":"exception"}
✔ fields read numbers, ranges, lists and steps (53.194565ms)
✔ the services' crons match when hosted g1t's would fire (1.944712ms)
✔ what is due is each matching cron of each service (0.406501ms)
✔ a run asks Wrangler for the handler, and a slow one is not doubled (40.206524ms)
✔ a deploy is announced to status.g1t.sh with the token, and without one nothing is sent (33.703339ms)
✔ an announcement that fails is a warning, never a failed deploy (0.77829ms)
✔ the stages run inside the window: started before, finished after, even when they throw; a dry run says nothing (1.090611ms)
✔ deploy.mjs announces every deploy, and the workflow passes it the token (0.52552ms)
ℹ tests 60
ℹ suites 0
ℹ pass 59
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 3916.558138
